home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Monster Media 1994 #2
/
Monster Media No. 2 (Monster Media)(1994).ISO
/
pcboard
/
dwnld30b.zip
/
TB_Q_PPE.NFO
< prev
Wrap
Text File
|
1994-04-01
|
2KB
|
32 lines
┌───────────────────┬───────────────────┐
│ │ ──────── │
└─────┐ ┌─────┤ ──────── │
└───────┘ └───────────────────┘
───═══╡ Thrust Brothers ╞═══───
TOPIC: The meaning of TB_Q_PPE support.
Well, everybody (hope so) outthere in the scene and outer knows the effect
of FILE_ID.DIZ or DESCRIPT.ION or similar files to this standart being
supported by BBS or tools. The systems scans this files and get their infos
out of. The idea of TB_Q_PPE is quiet the same to PPE's. One additional line
to each PPS source code would make the life a little bit easier. This line
just writes a 'Q' to the USERNET.XXX (accesable as UN_STAT()) and a short
description to the operation line (accessable as UN_OPER()). Due to the fact
that PCB doesnt use 'Q' as any switch right now, it can be used to mark any
action like 'T' for transfer or 'A' available for chat.
This additional line may look like:
wrunet pcbnode(),"Q",un_name(),un_city(),"Using: @X03NAME OF PPE," "
It's easy to add and provides some advantages.
So PPE's might write in e.g. the name of the PPE or the action they are
currently performing....or what ever they like to.
The syntax is quiet free, but max length (color codes included) musnt be
larger as 48 chars!....( operation line is not longer!)
Hope this idea will help to increase the possibility and features of PPE coding
and displaying infos to user. (HOPE CLARK wont use 'Q' one day!!!)